View Issue Details

IDProjectCategoryView StatusLast Update
0001923T99X171.00 SKB EagleSW Issuepublic2024-12-19 10:53
Reporter(ALTech) JunGyu Kim Assigned To(SW) Bcan Yeh Due Date2024-04-26 11:07
PrioritynormalSeveritys4-minorReproducibilityalways
Status closedResolutionfixed 
Summary0001923: Authentication code is not displayed as "*" in ATT deamon procedure
DescriptionHi Bcan,

HMSolution reported an issue that authentication code is not displayed as "*" in ATT daemon procedure.

Model : BFX-AT100
FW version : 15.541.66
ATT version : 240222

When I tested it, it worked normally in previous versions, but in version 240222, it is displayed as a number.
As far as I know, FXN added this feature.
https://btracker-cns.fii-foxconn.com/vaas/view.php?id=770#c3041

Please check this issue
Thank you.
Kim
TagsNo tags attached.
Attach Tags

Users monitoring this issue

Activities

(SW) Bcan Yeh

2024-04-19 12:02

developer   ~0015502

Hi Kim,

    Please provide the version number of "previous versions" that you tested.

(ALTech) JunGyu Kim

2024-04-19 12:12

developer   ~0015503

Last edited: 2024-04-19 12:14

Hi Bcan,

I have tested this issue on BFX-UH200 and versions are below

FW : 17.540.8
ATT : 240422

I will test it on BFX-AT100 and let you know the result.
Thank you.
Kim

(ALTech) JunGyu Kim

2024-04-19 12:20

developer   ~0015504

Hi Bcan,

I tested ATT 230214 version on BFX-AT100 v15.541.66.
When I activate ATT daemon through USB, the authentication code is still displayed number.

Is this a UI issue?
If yes, please explain in detail why this issue occurs.

Thank you.
Kim

(SW) Bcan Yeh

2024-04-19 14:15

developer   ~0015505

Hi Kim,

Here are your test results.
What is the result of Case C ?

A.
AttDaemon: 240222
FW: 15.541.66 (BFX-AT100)
=> It shows number

B.
AttDaemon: 230214
FW: 15.541.66 (BFX-AT100)
=> It shows number

C.
AttDaemon: 240422
FW: 17.540.8 (BFX-UH200)
=> What dose it show ?

(ALTech) JunGyu Kim

2024-04-19 14:26

developer   ~0015506

Hi Bcan,

C.
AttDaemon: 240422
FW: 17.540.8 (BFX-UH200)
=> It shows "*"

D.
AttDaemon: 230214
FW: 17.540.8 (BFX-UH200)
=> It shows "*"

Thank you.
Kim

(ALTech) JunGyu Kim

2024-04-19 15:08

developer   ~0015507

Hi Bcan,

FYI, When I test on BFX-UH200 v17.540.8, After activate ATT damon, UI was reset and authentication code shows as "*".
On BFX-AT100 v15.541.66, After activate ATT damon, UI is not reset and authentication code shows as number.

Please refer it.
Thank you.
Kim

(ALTech) JunGyu Kim

2024-04-22 10:51

developer   ~0015514

Hi Bcan,

Is there any update?
This issue should be fixed until early this week.

Please let me know the progress of this issue.
Thank you.
Kim

(SW) Bcan Yeh

2024-04-22 16:59

developer   ~0015519

Hi Kim,

To show auth code as "*", we need
1. set the property sys.skb.hidecert as 1
2. restart com.skb.tv

Currently the 2nd step failed.
I am still checking it.

(ALTech) JunGyu Kim

2024-04-24 08:26

developer   ~0015539

Hi Bcan,

This issue should be fix ASAP.
Please let me know the progress.

Thank you.
Kim

(SW) Bcan Yeh

2024-04-25 08:49

developer   ~0015563

Hi Kim,

After checking, there seems to be something wrong in the binder.
We need more time to check this issue.

(ALTech) JunGyu Kim

2024-04-25 09:49

developer   ~0015569

Hi Bcan,

If I test with the method below, it displayed as "*".

1. Activate ATT daemon and remove USB
2. After reboot, wait about 30~40 seconds for sys.skb.hidecert property as 1
3. Go to "비상 설정"
4. Input back key to go "B tv 인증" screen

It seems that the UI checks properties when entering the authentication screen.
As you mentioned, if binder communication is not possible, adding the above operation in ATT daemon may be a solution without UI modification.

Please note it.
Thank you.
Kim

(SW) Bcan Yeh

2024-04-30 15:51

developer   ~0015623

Hi Kim,

We have applied a workaround for this issue in BFX-AT100_5.4.2, BFX-AT100_5.4.1, and BFX-UA300_5.4.1.
You can refer to the commit "Update the way to trigger am command".
And please update AttDaemon.apk (in the usb disk) to version 240430.
AttDaemon release 240430 is uploaded to FTP server. (/release_by_fxn/AttDaemon)

(ALTech) JunGyu Kim

2024-05-02 17:12

developer   ~0015647

Hi Bcan,

I have tested in BFX-AT100_5.4.2, BFX-AT100_5.4.1, and BFX-UA300_5.4.1 and all branches are works well.

1. Please commit also to BFX-UH200_5.4.1, BFX-AT100_5.4.1_VCS branches.

2. Is it possible to just modify ATTdaemon without changing FW?
Because, BFX-UA300_5.4.1 and BFX-AT100_5.4.1_VCS FW was released on field.
It will be difficult to re-release FW because of this issue. Therefore, please check whether only ATTDaemon can be changed without changing FW.

Thank you.
Kim

(ALTech) JunGyu Kim

2024-05-03 10:04

developer   ~0015659

Hi Bcan,

HM Solutions is continuing to inquire about this issue.
As I mentioned in the comment, I am still inquiring about whether it is possible to modify only the ATT daemon without updating FW.

Would it be difficult to add the function that enter and exit another page to the ATT daemon, as I tested above?

Thank you.
Kim

(SW) Bcan Yeh

2024-05-03 15:04

developer   ~0015678

Last edited: 2024-05-03 15:04

Hi Kim,

1. For BFX-UH200_5.4.1, it works well without this workaround.
    For BFX-AT100_5.4.1_VCS, project vendor/foxconn refers to BFX-AT100_5.4.1.
    It's unnecessary to commit to these two branches.
2. For the method you provided, is there any other way (e.g. api?) to trigger page refreshing ?
    Inputting extra key code is not preferred for high uncertainty of UI.

(ALTech) JunGyu Kim

2024-05-03 15:50

developer   ~0015680

Hi Bcan,

1. It's unnecessary to commit to these two branches.
 >> Ok. Thank you for support.

2. Inputting extra key code is not preferred for high uncertainty of UI
>> As mentioned above, FW has already been released, so we need to find a way to do it temporarily.
As I know that there is no Page refreshing API.

As an alternative, HM Solution said to add the task of temporarily input extra key through the USER-CONTROL command.
But they said, currently USER-CONTROL is not working.

Could you please help to check why USER-CONTROL is not working?

Thank you.
Kim
image.png (150,833 bytes)   
image.png (150,833 bytes)   

(SW) Bcan Yeh

2024-05-03 17:32

developer   ~0015682

Hi Kim,

AttDaemon release 240503 is uploaded to FTP server. (/release_by_fxn/AttDaemon)
It adds extra keys to refresh authentication page for BFX-AT100/BFX-UA300.

(ALTech) JunGyu Kim

2024-05-03 18:07

developer   ~0015686

Hi Bcan,

Thank you for quick support.
On my side, it seems working well.
I will check again next week to see if on HM Solution is working properly.

For future reference, please also check why the USER-CONTROL command does not work.
Thank you.
Kim

(SW) Bcan Yeh

2024-05-09 10:00

developer   ~0015726

AttDaemon version 240503 is released.

(ALTech) JunGyu Kim

2024-05-09 10:57

developer   ~0015729

Hi Bcan,

I received word from HM Solutions that it works well.
We plan to operate ATT daemon as follows.

BFX-AT100 – 15.541.66 / BFX-UA300 – 19.541.520 -> Use 240503 version
BFX-AT100_5.4.2 / BFX-UH200_5.4.1 -> Use 240430 version

Thank you for support.

Additionally, Did you check why the USER-CONTROL command does not work?
There is no problem even if this command is not executed right now, I hope review it in advance for future reference.

Thank you.
Kim

Issue History

Date Modified Username Field Change
2024-04-19 10:13 (ALTech) JunGyu Kim New Issue
2024-04-19 10:13 (ALTech) JunGyu Kim Status new => assigned
2024-04-19 10:13 (ALTech) JunGyu Kim Assigned To => (SW) Bcan Yeh
2024-04-19 10:13 (ALTech) JunGyu Kim Issue Monitored: (ALTech) SY Yoon
2024-04-19 10:13 (ALTech) JunGyu Kim Issue Monitored: (ALTech) Younkwang Jung
2024-04-19 10:13 (ALTech) JunGyu Kim Issue Monitored: (ALTech) Sangmin Choi
2024-04-19 10:13 (ALTech) JunGyu Kim Issue Monitored: (ALTech) Wooshin Kang
2024-04-19 12:02 (SW) Bcan Yeh Note Added: 0015502
2024-04-19 12:12 (ALTech) JunGyu Kim Note Added: 0015503
2024-04-19 12:14 (ALTech) JunGyu Kim Note Edited: 0015503
2024-04-19 12:20 (ALTech) JunGyu Kim Note Added: 0015504
2024-04-19 14:15 (SW) Bcan Yeh Note Added: 0015505
2024-04-19 14:26 (ALTech) JunGyu Kim Note Added: 0015506
2024-04-19 15:08 (ALTech) JunGyu Kim Note Added: 0015507
2024-04-22 10:51 (ALTech) JunGyu Kim Note Added: 0015514
2024-04-22 16:59 (SW) Bcan Yeh Note Added: 0015519
2024-04-24 08:26 (ALTech) JunGyu Kim Note Added: 0015539
2024-04-25 08:49 (SW) Bcan Yeh Note Added: 0015563
2024-04-25 09:49 (ALTech) JunGyu Kim Note Added: 0015569
2024-04-30 15:51 (SW) Bcan Yeh Note Added: 0015623
2024-05-02 17:12 (ALTech) JunGyu Kim Note Added: 0015647
2024-05-03 10:04 (ALTech) JunGyu Kim Note Added: 0015659
2024-05-03 15:04 (SW) Bcan Yeh Note Added: 0015678
2024-05-03 15:04 (SW) Bcan Yeh Note Edited: 0015678
2024-05-03 15:50 (ALTech) JunGyu Kim Note Added: 0015680
2024-05-03 15:50 (ALTech) JunGyu Kim File Added: image.png
2024-05-03 17:32 (SW) Bcan Yeh Note Added: 0015682
2024-05-03 18:07 (ALTech) JunGyu Kim Note Added: 0015686
2024-05-09 10:00 (SW) Bcan Yeh Status assigned => resolved
2024-05-09 10:00 (SW) Bcan Yeh Resolution open => fixed
2024-05-09 10:00 (SW) Bcan Yeh Note Added: 0015726
2024-05-09 10:57 (ALTech) JunGyu Kim Note Added: 0015729
2024-12-19 10:53 (ALTech) JunGyu Kim Status resolved => closed